home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000217-20000824
/
000341_news@columbia.edu _Fri Jun 2 14:38:41 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by monire.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id OAA24274
for <kermit.misc@cpunix.cc.columbia.edu>; Fri, 2 Jun 2000 14:38:41 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA08253
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 2 Jun 2000 14:38:40 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id OAA07924
for kermit.misc@watsun.cc.columbia.edu; Fri, 2 Jun 2000 14:16:08 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: locked files
Date: 2 Jun 2000 18:16:04 GMT
Organization: Columbia University
Message-ID: <8h8tl4$7nh$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <3937D24E.42772371@ttuhsc.edu>,
Mike Collins <csjmc@ttuhsc.edu> wrote:
: I am using the syncronize script from the kermit script library and need
: a way to tell it to ignore locked file(transfers dy at that point). I
: have looked in the c-kermit manual but must have missed it.
:
As Jeff said, maybe we can look into adding such a capability. What
operating system do you have? Different OS's have different ideas of what
is meant by "locked". However, as far as I know, the fact that a file is
locked does not mean that it can't be read, and therefore that it can't be
sent.
Or do you mean that the copy of the file on the receiving end is locked?
But it needs to be replaced, because the copy on the sending end is newer?
In any case, it seems to me that the synchronize script should either do its
job or fail. If it only partially does its job, it hasn't synchronized the
two ends -- how would you know what it did and did not do, unless you are
willing to keep and read a transaction log every time you run the script?
So it might make more sense to run the synchronize script in a loop until it
succeeds, pausing between each run long enough to give any locked files a
chance to become unlocked. This doesn't cost anything extra, since the
files that were already transferred won't be transferred again.
>From a practical point of view, if we wanted to implement the capability
to skip locked files, we'd need to know exactly what happens when we try to
overwrite such a file? What error code is returned, and can it be
distinguished from other kinds or errors, like "lacks write permission", etc?
- Frank